Thai Airways International

Safety profile and incident history for Thai Airways International.

Safety Score

7.6/10

Total Incidents

16

Total Fatalities

382

Recent Incidents

Airbus A350-941

en route MUC-BKK -

Thai Airways flight TG925, an Airbus A350-941, was en route between Munich (MUC) and Bangkok (BKK) when the aircraft experienced turbulence. Four occupants suffered serious injuries, one suffered minor injuries.

Airbus A330

Bangkok-Suvarnabhumi Samut Prakan (<U+0E2A><U+0E21><U+0E38><U+0E17><U+0E23><U+0E1B><U+0E23><U+0E32><U+0E01><U+0E32><U+0E23>)

Following an uneventful night schedule service from Guangzhou, the crew was cleared for an ILS approach to runway 19L at Bangkok-Suvarnabhumi Airport. Following a smooth landing, the crew started the braking procedure when, after a course of about 1,000 metres, the aircraft deviated to the right then veered off runway. While contacting soft ground, the nose gear collapsed, the aircraft sank in earth and came to rest with both engines in flames. All 302 occupants were rescued, among them 14 passengers were injured. The aircraft was damaged beyond repair.

March 3, 2001 1 Fatalities

Boeing 737-400

Bangkok-Don Mueang Bangkok City District

While parked at gate 62 at Bangkok-Don Mueang Airport, the aircraft suffered an explosion and caught fire. On board were eight crew members awaiting 148 passengers to embark, among them Thaksin Shinawatra, Thai Prime Minister. Seven crew members were able to evacuate the cabin while the eighth crew member died. The aircraft was completely destroyed by fire. It was reported that the first explosion occurred in the center fuel tank, about 27 minutes prior to the expected takeoff time, followed by a second explosion in the right wing tank 18 minutes later.

December 11, 1998 101 Fatalities

Airbus A310

Surat Thani Surat Thani (<U+0E2A><U+0E38><U+0E23><U+0E32><U+0E29><U+0E0E><U+0E23><U+0E4C><U+0E18><U+0E32><U+0E19><U+0E35>)

Thai Airways International flight 261, an Airbus A310, left Bangkok-Don Mueang International Airport, Thailand at 17:54 hours local time for a domestic flight to Surat Thani. At 18:26 hours, the copilot first established contact with the Surat Thani approach controller while the aircraft was 70 nautical miles away from Surat Thani Airport. The controller radioed that the crew could expect a VOR/DME instrument approach to runway 22. At that time surface wind was calm with a visibility of 1500 meters, light rain and a cloud base of 1800 feet. At 18:39 hours the copilot contacted Surat Thani aerodrome controller and reported over the Intermediate Fix (IF). The controller informed him that the precision approach path indicators (PAPI) on the right side of runway 22 were unserviceable while the left lights were in use. At 18:41 hours, the copilot reported passing final approach fix (FAF). The controller informed the pilot that the aircraft was not in sight but it was cleared to land on runway 22. The surface wind was blowing from 310 degrees at a velocity of 5 knots so the pilots should be careful or the slippery runway. At 18:42 hours, the copilot reported that the runway was in sight and later on the controller also had the aircraft in sight. The pilot decided to go-around. The controller asked the pilot about the distance where the runway could be seen. The copilot reported that it could be seen at 3 nautical miles and requested for the second approach. The controller requested to report over FAF . When the copilot reported that the flight was over the FAF again, the controller cleared the flight to land although he again could not see the runway. When the flight crew failed to observe the runway lights, the captain decided to go around again. Again the controller instructed the flight to report over the FAF and reported that visibility had decreased to 1,000 meters in light rain. At 19:05, after reporting over the FAF, the flight was cleared to land on runway 22. The flight maintained the Minimum Descent Altitude (MDA) but the crew were unable to see the runway. The autopilot was disconnected and a little later the captain decided to go around. The pitch attitude increased continuously. The pitch attitude reached approximately 40°, when the pilot applied the elevator decreasing the pitch attitude to 32-33°. When he discontinued applying elevator the pitch increased to 47-48°. Consequently the speed decreased to 100 knots. The captain was not aware of the attitude due to stress and the expectation that the go around was flown exactly like the first two go-arounds. The airplane lost altitude until it impacted terrain to the left of the runway. 45 people survived and 101 others were killed, including 11 crew members.

July 31, 1992 113 Fatalities

Airbus A310

Kathmandu Bagmati

Thai Airways Flight 311 was conducting the Sierra (VOR/DME) approach to runway 02 at Tribhuvan International Airport, in instrument weather conditions. A flap fault occurred while the flight was on the approach; this caused the crew to ask for clearance back to Calcutta, a decision that was in keeping with both Company and performance requirements, which necessitate the use of full flaps for the steep final approach. Shortly (21 seconds) after making this request, at a distance of approximately 12 nm from the Kathmandu VOR, the flap fault was rectified by retracting and then reselecting the flaps. The crew determined that it was not possible to continue the straight-in approach, due to the steep descent angles required and the position of the aircraft. The crew stated to the control tower that they wished to start their approach again and requested a left turn back to the Romeo fix, which is 41 nm south south-west (202 radial) of the Kathmandu VOR. The Controller, in the non-radar environment, responded by clearing the flight to make the Sierra approach, which starts at the 202 radial and 16 nautical miles from the VOR. The crew response to the clearance was to report that, at the moment, they couldn't land and to ask again for left turn back to Romeo to start their approach again. After further dialogue with the controller, which included requests for a left turn, the crew unilaterally initiated a right turn from the aircraft's 025° heading and commenced a climb from an altitude of 10,500 feet to FL180, when the flight was about 7 nm south of the Kathmandu VOR. The crew reported to the tower controller that the flight was climbing and the controller replied by instructing the crew to report at 16 nm for the Sierra approach. During the turn, there was more discussion between the tower controller and the flight, where it was established that the aircraft was to maintain an altitude of FL115 and was to 'proceed to Romeo' and contact the Area Control Center (ACC) controller. The flight, commencing a descent while in the turn, completed a 360° turn, momentarily rolling out on headings of 045° and 340°, and again proceeded toward the north on a heading of 025° magnetic. When the flight was about 5 nm south-west of the Kathmandu VOR, the crew contacted the ACC and stated that the aircraft was 'heading 025' and they wished to proceed to Romeo to start their approach again; adding they had 'technical problems concerned with the flight.' It was again established that the flight was to proceed to Romeo and the crew agreed to 'report over Romeo.' It was determined from the cockpit voice recorder that the crew was in the process of inserting 'Romeo' and other related navigational information in the Flight Management System, but were experiencing difficulties. The flight continued towards the north on a heading of 025° and then, at about 16 nm north, the heading was altered to the left to 005°. Slightly over one minute later, the Ground Proximity Warning System (GPWS) sounded the warning 'terrain, terrain' followed by 'whoop whoop pull-up'; the aural warning continued until impact approximately 16 seconds later. Engine thrust was increasing and 'Level Change' had been announced on the cockpit, just before the impact occurred at the 11,500-foot level of a 16,000-foot peak; the accident site was located on the 015 radial (north-north east) at 23.3 nm from the Kathmandu VOR. The aircraft was destroyed and all 113 occupants were killed.

Avro 748

Udon Thani Udon Thani (<U+0E2D><U+0E38><U+0E14><U+0E23><U+0E18><U+0E32><U+0E19><U+0E35>)

After landing, the aircraft was unable to stop within the remaining distance, overran and came to rest. There were no casualties but the aircraft was damaged beyond repair.

August 31, 1987 83 Fatalities

Boeing 737-200

Phuket Phuket (<U+0E20><U+0E39><U+0E40><U+0E01><U+0E47><U+0E15>)

Thai Airways Flight 365 was approaching Phuket VOR/DME on radial 119 after a flight from Hat Yai. At the same time Dragon Air Flight 203 (a Boeing 737 registered VR-HYL, carrying 62 occupants) also approached Phuket VOR/DME on radial 090. At 08:34 UTC Dragonair 203 reported at 2500 feet with Thai 365 in sight in front of them. The Thai Boeing was flying at 3000 feet at the time, and was 13 miles from Phuket VOR/DME. Dragonair 203, first priority in approach sequence, then turned right at 12 DME and was going to turn inbound for finals for runway 27. The Thai crew surmised that the other crew were making a false position report to gain landing priority and reported hurriedly that they were at 8 DME inbound and requested visual approach, though they hadn't reached 8 DME yet. This forced Phuket Approach to give Thai 365 landing priority at 08:35. The Dragonair crew (flying IFR) immediately warned that the Thai plane couldn't descend through their flight level. Concentrating on the conflicting traffic the speed decayed to 163 knots until the stick shaker activated. The Thai crew then applied power and raised the landing gear, but the aircraft entered a stall crashed into the sea, disintegrating on impact. All 83 occupants were killed.

Avro 748

Chiang Rai Chiang Rai (<U+0E40><U+0E0A><U+0E35><U+0E22><U+0E07><U+0E23><U+0E32><U+0E22>)

Following an uneventful flight from Chiang Mai, the crew initiated the approach to Chiang Rai Airport in good weather conditions. The copilot was the pilot-in-command when the aircraft completed a gear up landing. It slid on runway for about 1,075 meters before coming to rest on the runway. All 43 occupants escaped uninjured while the aircraft was damaged beyond repair.

April 15, 1985 11 Fatalities

Boeing 737-200

Phuket Phuket (<U+0E20><U+0E39><U+0E40><U+0E01><U+0E47><U+0E15>)

Following an uneventful flight from Bangkok, the crew started the descent to Phuket Airport by night and good weather conditions. Four minutes after being cleared to descend to 3,000 feet, the pilot reported that he was unable to receive the DME signal. ATC asked the crew if he wanted to conduct a VOR approach to runway 09 but the captain preferred to attempt a visual approach to runway 27. On final, the aircraft struck a hill (800 feet high) and crashed about 18 km short of runway. The aircraft was destroyed and all 11 occupants were killed.

Avro 748

Chiang Rai Chiang Rai (<U+0E40><U+0E0A><U+0E35><U+0E22><U+0E07><U+0E23><U+0E32><U+0E22>)

After touchdown at Chiang Rai Airport, the airplane encountered difficulties and was unable to stop within the remaining distance. It overran and came to rest in a ditch. All 21 occupants were evacuated, some of them were injured.

Page 1 of 2

Airline Information

Country of Origin

Thailand

Risk Level

Low Risk